Specifications automation system and method

ABSTRACT

A method of leveraging computer technology to guide the user to create, display, and edit architectural and engineering information in ways specific to the architect&#39;s or engineer&#39;s needs in specification development is provided. This is provided in software that allows the automatic creation and management of architectural and/or engineering workflows, including but not limited to: procurement, quality assurance, and design, driven by engineering specifications and requirements contained therein and therewith. For each specification paragraph, in addition to the main textual component, appropriate attributes and/or elements are created and defined by a schema to support multitasking and the storing of related information for related purposes.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional application No. 61/341,360 filed on Mar. 29, 2010, which is incorporated herein by reference as if fully set forth.

BACKGROUND

Technical specifications or engineering specifications used in various industries are static documents, typically produced using a word processor. These documents contain numerous references to codes, standards and other specifications. They also contain references to other kinds of documents that are intimately related, such as equipment datasheets, inspection and test requirements, bills of material, and other engineering, procurement, and project management documents. In many cases the main engineering specifications are the governing documents, while the information on other closely related specifications and other intimately related documents becomes out-of-spec because they are treated as separate documents.

It would be desirable if the user experience of individuals who write, read, and/or act on technical specifications was both more powerful for managing engineering information and engineering workflows, and at the same time more simplified in editing from typical systems (e.g. word processing) that are in use today.

SUMMARY

The invention relates to a method of leveraging computer technology to guide the user to create, display, and edit architectural and engineering information in ways specific to the architect's or engineer's needs in specification development.

The invention also relates to the automatic creation and management of architectural and/or engineering workflows, including but not limited to: procurement, quality assurance, and design, driven by engineering specifications and requirements contained therein and therewith.

Additionally, the invention relates to business, design, and specification development methods that enhance the style and usefulness of engineering and architectural specifications.

Furthermore, this invention relates to the design and development of computer software and user interface, and configuration files that enable the application of said methods.

For the above cited reasons it is an object of the invention to provide both a datamodel and computer software to enable engineers and other professionals and responsibilities to “multitask”, that is, create several documents for various purposes and workflows and business requirements from a single editing session.

For the datamodel, for each specification paragraph, in addition to the main textual component, the appropriate attributes and/or elements are created and defined by schema to support said multitasking and the storing of related information for related purposes.

For the computer program and user interface, the ability for the user to write the main textual components of the specification while having simultaneously in view the content of the various metadata, as necessary, and being able to edit all at the same time

Applicable to both datamodel and user interface, is the automatic linking and electronic management of the relationships of each paragraph and its metadata, as well as the ability to publish the main spec and its related sub-specifications and/or documents automatically.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1

FIG. 1 shows an application window with “View” Drop down on the toolbar shows there are now 2 Business Group specific views of the document available. Views are dynamic and automatically appear based on the XML tags that have been applied to the document, and demonstrate an example of MULTI-PURPOSE specifications.

FIG. 2

FIG. 2 shows Linkage of related objects.

FIGS. 3, 4, and 5

FIGS. 3, 4, and 5 show various modes of side-by-side and in-line specification comparisons. FIG. 3 shows a four-way overlay driven by specification paragraph number. FIG. 4 shows an in-line difference based on “multi-purpose” specification selection (a Corporate Business Unit in this case), where all of the specifications and/or requirements that are not applicable to the business unit appears as stricken-out in different color. FIG. 5 show a side-by-side comparison of a multi-purpose specification, showing which specifications and/or requirements are applicable to which corporate business unit, and how they compare to each other.

FIG. 6

FIG. 6 depicts a Persistable workflow wizard.

FIG. 7

FIG. 7 depicts a “bid tabulation”.

FIG. 8

FIG. 8 depicts the specification migration process.

FIG. 9

FIG. 9 depicts migration and lifecycle specification management for and/or with a PLM (Product and/or Plant Lifecycle Management) system.

FIG. 10

FIG. 10 depicts the specification editor.

FIG. 11

FIG. 11 depicts Datasheet Automation.

FIG. 12

FIG. 12 depicts a Library Matrix

DETAILED DESCRIPTION

MULTI-PURPOSE SPECIFICATIONS. The system automatically detects user context for current specification and sets-up context specific views. Choices for context can be system defined, external configuration file defined, or ad-hoc defined by the user at time of use, or any combination thereof.

LINKAGE OF RELATED OBJECTS. The system allows the user to link spec objects to other spec objects and/or other contexts and/or objects.

COMPARISONS. As a matter of prior art, software developers have long utilized a system called “differencing”, or “diff”, for comparing text (typically source-code files) documents. Differencing can be in-line or side-by-side, and is typically colorized to visually compare and contrast similar documents. This invention claims the method of displaying diff specific to specifications and specification workflows, such as “spec overlays”, “exception specs”, “comments, exceptions and clarifications to specifications”, and “multi-purpose” specifications. In the prior art of text-based diff, the differencing logic is driven “the line of text”. This invention claims the innovation of driving diff based on the specification datamodel and XML tagging, and being able to compare spec information based on paragraph and/or section number, textual content, and/or workflow metadata such as submittals, QA requirement, and Data specifications. Furthermore, this invention incorporates the specification-specific differencing of two OR MORE views simultaneously.

PERSISTABLE WORKFLOW WIZARDS. Package an entire workflow so that not only is it resume-able, it is also portable (you can post it, email, etc., and someone else can continue the workflow, then pass it on, or return, and so on). We think that this will pose a huge ease-of-use feature to minimize software training for specialists and suppliers. For example, consider the following workflow:

-   -   Spec master begins migration of disparate word files by taking         steps in the wizard such as         -   Paragraph structure definition         -   Initial conversion         -   Structure and Formatting observation, correction, massaging,             etc.     -   Spec Master saves the workflow and emails it to a Fire         Protection Expert to review the documents and see if they can be         combined.     -   Fire Protection Expert simply opens the file he received, and it         immediately loads into a workflow wizard that is poised to walk         him through the file review and combination process.         -   Fire protection expert simply has to follow the instructions             in each step, without having to neither read anything nor             learn anything new . . . nor fumble around with a new set of             application menus with which he is not familiar.         -   The steps will carefully walk the Fire Protection Expert             through the tagging process so that his thoughts and             combination logic are captured on the content. The             application will be completely responsible for data             integrity, minimizing the possibility of user error. The             information will be collected in some simple way, e.g.             “Please provide description for documents on the left” (he             inputs “Single Story”); “Please provide description for             documents on the right” (he inputs Multi-Story), and so on.             We will create the custom tags automatically from the             descriptions.     -   Fire Protection Expert saves his workflow and emails it back to         the Spec Master.     -   The Spec Master can go <Back> and <Next>, scrolling through the         expert's workflow, to see exactly what he did. Make corrections,         optimizations.     -   Then publish and end workflow . . .         In this way we are creating architecture for “person         responsible” to set up, drive, and make it really easy for         various dependencies to provide their input (another example,         supplier comments and/or acceptance of the documents).         We also have a strategy to make workflows configurable by the         Spec Master to designate the steps and those responsible for the         steps (e.g. only Fire Protection Expert can touch content tagged         as “Fire Protection”, and the pump guy can only touch the         hydraulics, and the metallurgist can only touch paint and         welding, and so on).

DESIGN AND/OR BID TABULATION. This invention is built on the COMPARISONS and/or PERSISTABLE WORKFLOW WIZARDS to automate side-by-side (AKA ‘apples-to-apples’) comparisons of design details and/or requisitions and/or proposals.

MIGRATION (CONVERSION AND VALIDATION). Migration is the process of reading (AKA “parsing”) existing specs, in some cases well-formatted, in some cases poorly formatted, “scrubbing”, “normalizing”, and converting to well-formed “specx” XML.

Migration utilities are intended primarily for Administrators, Spec Masters, Department Leads, etc., and are generally necessary only for one-time use in preparing legacy specs for the new system. Day-to-day users may, in some cases, also use the migration utilities for local migration(s) and/or follow-up processing of additional content. Migration, conversion, and/or validation steps may be menu and/or ribbon driven from the main user interface or Persistable Workflow Wizard driven.

EDITOR. Specification Editor optimized for Architects and Engineers. Editing optimized for the professional spec writer/spec master. Editing simplified for architects, engineers, and project managers. Editing enforces “whole paragraphs” and/or “meaningful fragments” as defined in XML model. Editor provides feedback with color and border around whole paragraph, current fragment, and workflow-specific metadata as applicable. Editor does allow user to violate corporate and/or document styles nor formats, nor the underlying XML schema.

CENTRALIZED REFERENCES SECTIONS. This is implemented as “Proxy Specs”, i.e., documents that contain references to external standards (external to a company, external to the library, external to any context of collection) and the rest of the documents in ‘the current set’ point to. Specification Automation System and Method provides specific support and ‘productization’ of this concept and functionality.

DATASHEET AUTOMATION. Specification Automation System and Method provide support for linking specification objects with “datasheets”, AKA “spec-sheets”. This invention provides a user who is working on or with datasheets to conveniently reference the pertinent narrative specification object(s) by tooltip, hyperlink, button, and/or similar automated manner.

LIBRARY MATRIX. Specification Automation System and Method creates a dynamic table of contents of a specification library. The tabular definition may come from an external system such as a spreadsheet or a traditional document table of contents, or created from within the software. Library Matrix allows user to show columns selectively, see a preview of the selected document, single or multi-select documents, and/or import and/or export and/or create specification libraries.

The system is implemented utilizing a PC or other computer processor programmed with the specific method according to the invention. 

1. A method of automatic discovery of multiple business and/or context specific views based on single specification representation loaded in computer memory, said method comprising the steps of: a) Detecting user definition of specification-related metadata; b) Automatically inferring and populating view choices; c) Collapsing or expanding the current view of the current document according to user view selection.
 2. A method of providing convenient user interface to view multiple objects simultaneously and creating links between them, said method comprising the steps of: a) Viewing multiple specification objects; b) Defining links between objects; c) Following links between objects interactively; d) Creating views and/or or reports that are based on links and/or link definitions.
 3. A method of specification-specific comparisons and differencing (diff), said method comprising the steps of: a) Programmatically calculating the difference between documents and/or contexts within documents (e.g. different purposes in a multi-purpose specification; similarly numbered paragraphs of a specification and its overlay, etc.); b) Whereas the difference is not driven by just text, but primarily by specification context, datamodel, and/or associated metadata; c) Displaying the difference side-by-side and/or in-line; d) In side-by-side mode, two or more parallel differencing windows can be displayed; e) In side-by-side mode of more than two displays, the difference depicted by each window in the 3rd position or higher, may depict the difference of either it to the left-most window or to the window immediately to its left. 4.-10. (canceled) 